Accounts Receivable
| Application Setting | Data Type/ Value Type | Comment | Action |
|---|---|---|---|
| 3rd Party Cashiering allows Bill Number only lookup? | Effective Date/Boolean | Determines if the Cashiering API call to get an amount due will support input of a BillNumber without a Tax Year. | The default is false. Set to true only if the jurisdiction or vendor that is interfacing with the API is unable to support the TaxYear+BillNumber as the unique identifier for a tax bill. If set to True, Aumentum must also be configured in the Levy module with "Use Consecutive Bill Numbers" set to True, so that Aumentum will always create consecutive bill numbers regardless of tax year. Converted bill numbers must also be unique. |
| 3rd Party Cashiering GetAmountDue returns PIN information only | Effective Date/ Boolean | Determines the amount of data returned for the GetAmountDue API call. | The default is false. Set to true only if 3rd Party Cashiering APIs are being used AND the jurisdiction wishes only PIN-level information to be returned in the request for amount due. False means the request will return all possible details in the XML, including the tax bill breakdown and allocations and flag information. True will improve performance, since less data is being returned. |
| 3rd Party Cashiering provides Transaction Id | Effective Date/ Boolean | Generates a unique transaction id in the AmountsDue XML, accepts the transaction id and stores it with payment for the Payment XML string. Data is stored in PmtINfo table, in ConfNumber field. | Set to TRUE if the APIs should provide, and accept and store with payment, a unique transaction ID. Set to FALSE if not required. |
| Adjust tax bill dates during correction | Effective Date/ Boolean | (Palm Beach only) for grace period, determines whether to adjust tax bill dates during correction. | The default is false. Set to true only to adjust the tax bill date during correction. For Palm Beach only, the installment schedule uses the correction date as the basis for discounts and interest to accommodate the discount grace period and interest grace period. |
| Allow reverse on batch collection payment import | Effective Date/ Boolean | Enable or disable the [Reverse] button for Batch Collection Payment Imports except Excise Tax Payment Import. | Reverse is designed to be used immediately after a batch collection payment import completes, if the jurisdiction realizes a mistake was made and the payment file should not have been imported. Reversing will delete the payment import information from the last import. Should be set to FALSE if the jurisdiction uses payment imports for payments towards (new) payment plans, payment imports using surplus as tender, or payments towards tax sale. |
| Allow reverse on Excise Tax payment import | Effective Date/ Boolean | Enable or disable the [Reverse] button for Excise Tax Payment Import. | Set to TRUE for Washington state only. Reverse is designed to be used immediately after the Excise Tax Payment Import completes, if the jurisdiction realizes a mistake was made and the payment file should not have been imported. Reversing will delete the payment import information from the last import. Should be set to FALSE if jurisdiction is not in Washington state. |
| Apply final plan payments in batch collections to bills in plan | Effective Date/ Boolean | Used for payment plans that hold plan payments as surplus until the plan is paid in full. Will apply surplus amounts on a payment plan that is paid off through batch collection payment imports to be applied to the tax bill. | Default is true to apply any surplus amount on a payment plan that is paid off through batch collections to be applied to the tax bill. |
| AR Audit Final Status | Effective Date/ Systype | Determines which Surplus Audit Status is considered 'final'. Once this status is selected and saved, no further changes may be made to the audit; it becomes view-only. | Set to 'Completed', or an alternate audit status created by the jurisdiction that is considered the 'final' status. |
| AR Export File Location | Effective Date/ String | (California only) Defines the Accounts Receivable export location for the of Remittance Combined Installment Export batch process. This controls the default location where the system saves the export file. | Define the export file location as applicable to your jurisdiction. Enter a valid network location, for example: \\VSBATIMP04_AumentumBatchService_CA_SBA_Production\ARExport |
| AR Export File Name | Effective Date/ String | (California only) Define the Accounts Receivable export file name for the of Remittance Combined Installment Export batch process. This controls the default file name format. | Define the export file name as applicable to your jurisdiction. You can specify a file name, use predetermined values, or a combination of both. Values available are Process, Date, Datetime, Sequence, and User. The process uses the short description of the export process (systype category 'AR Process'). The format is to use brackets around predetermined values, The default is [Process]-[Date]-[Sequence]. |
| Automatic payment reallocation options | Effective Date/ Systype | Automatic reallocation of payments occurs when charge adjustments cause charges to be reduced, which generates a negative balance situation in which existing payments for a revenue object are greater than its charges. The system must remove the payment to allow the charge adjustment to occur. This setting indicates how to handle this situation - either by performing a fully automated reallocation of the payment, or by cancelling the payment and creating a surplus. (The surplus can then be reallocated manually by the user at a later time.) | If the application setting is set to Allow automatic reallocation of paymentsand the Apply Cashiering Global Partial rulescheckbox on the Set Up Automatic Reapply of Payments screen is checked, the partial payment cashiering rules apply. If the application setting is set to Allow automatic reallocation of payments and the checkbox is notchecked, the partial payment cashiering rules are ignored. If the application setting is set to Allow automatic cancel of payments and creation of surplusthe payment goes to surplus. |
| Automatically remove/adjust receivable discount | Effective Date/ Boolean | Indicates whether a discount should automatically decrease when the Payment Terms calculation is performed after being posted to financial detail and considered a receivable. The discount is always allowed to increase. | Set to true if discounts can decrease or increase after posting as a receivable in financial detail. Setting to ‘false’ only allows increases if the calculation indicates an increase is necessary. A setting of ‘true’ allows both increases and decreases. The default is ‘false’. |
| Automatically remove/adjust receivable interest | Effective Date/ Boolean | Indicates whether interest should decrease automatically when the Payment Terms calculation is performed after being posted to financial detail and considered a receivable. Interest is always allowed to increase. | Set to True if interest can decrease or increase after it has been posted as a receivable in financial detail. This allows removal of interest that has already been calculated when receiving back dated bill payments. A setting of False only allows increases if the calculation indicates an increase is necessary. A setting of 'true’ allows both increases or decreases. |
| Automatically remove/adjust receivable penalty | Effective Date/ Boolean | Indicates whether penalty should decrease automatically when the Payment Terms calculation is performed after being posted to financial detail and considered a receivable. Penalty is always allowed to increase. | Set to true if penalty can decrease or increase after it has been posted as a receivable in financial detail. This allows removal of penalty that has already been calculated when receiving back dated bill payments. A setting of 'false’ only allows increases if the calculation indicates an increase is necessary. A setting of True allows both increases or decreases. The default is ‘false’. |
| Block payments during batch payment processing | Effective Date/ Boolean | Determines whether to add a flag to each bill indicating payment is pending during the Run Process step of the mass payment process. This flag prevents other methods from posting a payment. Once mass payment is posted, the flag is removed. | Set to True to add the flag and to prevent other methods from posting a payment. The default is False. See also the application setting Flag to use for batch payment blockingas that application setting is used in combination with this application setting. |
| Business date is distribution date | Effective Date/ Boolean | Default - true - uses the business date as the distribution date for a payment transaction. When false, you must then specify the distribution date on payment management screens; also the effective pay date is used for the distribution date when collecting new payments. | Set to True to use the business date as the distribution date. Set to False to manually assigned the distribution date for payment management. Default is True. |
| Cashiering amount date | Effective Date/ Systype | This setting determines which charges to include in the default "due" amount for Aumentum Cashiering Collect Payments screen. This setting will also affect the Total Due panel in Info Center, determining whether an installment amount shows as Current or Delinquent. This setting also will affect Tolerance (over/short) functionality. Date choices must be previously set up in the Functional Calendar. Jurisdictions having multiple installments need to use this setting. | Select the functional calendar event type to use for the "due" amount on Aumentum Cashiering's Collect Payments screen. This must be a date that is configured and appears on all bills. |
| Certificate refund interest rate |
Effective Date/ Decimal |
(Florida only) Set to the annual refund interest rate for tax sale certificates. | (Florida only) If the corrected bill that results in a surplus is a tax sale bill (identified by CalcTaxSaleRefundInt on the surplus table), Aumentum will use the Refund Interest Rules to determine if the surplus should calculate Refund Interest. If yes, the system will look at the 'Use certificate interest rate if less than refund interest rate' application setting. If it is False, then the rate in the 'Certificate refund interest rate' application setting will be used. If it is True, then the rate from the 'Certificate refund interest rate' application setting will be compared to the rate from the refund interest rule, and the system will use the lower rate. The start date of the refund interest calculation will be determined by the 'Certificate refund interest start calculation event type'. Note: The rate entered will be divided by 12, and the refund interest calculation will be # of months x rate x surplus amount. Refund Interest for tax sale bills will be broken out and stored in the RefundIntDist table, using logic specific to Florida Lien Sale. |
| Certificate refund interest start calculation event type | Effective Date/ Systype | (Florida only) Set to the date event type that is to be used to determine the start date for calculation of refund interest for tax sale certificates. | (Florida only) If the corrected bill that results in a surplus is a tax sale bill (identified by CalcTaxSaleRefundInt on the surplus table), Aumentum will use the Refund Interest Rules to determine if the surplus should calculate Refund Interest. If yes, the system will look at the 'Use certificate interest rate if less than refund interest rate' application setting. If it is False, then the rate in the 'Certificate refund interest rate' application setting will be used. If it is True, then the rate from the 'Certificate refund interest rate' application setting will be compared to the rate from the refund interest rule, and the system will use the lower rate. The start date of the refund interest calculation will be determined by the 'Certificate refund interest start calculation event type'. Note: The rate entered will be divided by 12, and the refund interest calculation will be # of months x rate x surplus amount. Refund Interest for tax sale bills will be broken out and stored in the RefundIntDist table, using logic specific to Florida Lien Sale. |
| Charge code for bad check | Effective Date/ Systype | Indicates the default user defined description for the charge. No default value is specified. Charge codes are systypes set up through Configuration> Systypes. This charge type is used as the default, if a NSF Fee is not configured under Tax> Accounts Receivable> Setup> NSF Fee Setup. | Select the default charge code to use for a bad check fee. NOTE: This application setting only impacts Fees that are added during the Accounts Receivable Bad Check process. Also see the application setting Charge sub-code for bad check |
| Charge sub-code for bad check | Effective Date/ Systype | Indicates the default description for the subtype of charge. Charge sub-codes are systypes set up through Configuration>Systypes. This charge type is used as the default, if a NSF Fee is not configured under Tax> Accounts Receivable> Setup> NSF Fee Setup. | Select the default charge sub-code to use for a bad check fee. Default is Gross. NOTE: This application setting only impacts Fees that are added during the Accounts Receivable Bad Check process. Also see the application setting Charge code for bad check. |
| Combine refunds during the refund workflow batch process | Effective Date/ Boolean | Determines whether the system is to automatically combine surplus being refunded to the same name/address into a single refund, when configured to automatically refund. |
Default is False. If set to True, during the Surplus/Refund Routing Process if more than one surplus is identified as having exact same name/address AND the routing rules are configured to automatically create the refund, the system will combine the surplus into a single refund. If set to False, each surplus will be a separate refund. |
| Cost Charge Code | Effective Date/ Systype | (California only.) Indicates the charge code of the charge that is considered 'Cost'. Charge codes are systypes set up through Configuration> Systypes. | The 'Cost' charge is a California charge added to the 2nd installment of Secured bills when unpaid after their due date, per statute 4653.8. |
| Date for surplus search source bill enrollment date | Effective Date/ Systype | Select a date type that determines the enrollment date of the bill. |
Select a date type that is configured in the Functional Calendar and appears on all bills for the jurisdiction. In California, set to 'Mail Date' if this date is configured and used by the county. Used by the Accounts Receivable Search function, when searching for Surplus or Refunds, If the fields 'Starting Enrollment Date of Source bill' and 'Ending Enrollment Date of Source Bill' are entered as criteria. |
| Date when charges go delinquent | Effective Date/ Systype | Date type on which charges go delinquent. Available values are of the systype category Bill Date Type, which contains systypes such as Bill Date, Due Date, and Print Date. Date choices must be previously set up in the Functional Calendar. | Set a date type configured in the Functional Calendar for all bills. No default value is specified. No longer determines Current vs Delinquent in Info Center See also Cashiering amount date |
| Default bad check flag | Effective Date/ Systype | The flag type used as default for bad checks. Flag type selected must be applicable to tax bills, parties, or revenue objects (or a combination of those). Choices are flags set up through Configuration; Flags. | Set the default flag type for bad checks. Default value is NSF. |
| Default Interest Calc Display | Effective Date/ Systype | For Colorado jurisdictions, determines the text displayed on an F/I (full payment or installment) toggle button in Info Center >Tax Information screen, Bill Detail screen, and View Delinquents screen as well as on the Cashiering Collect Payments screen. The button toggles between viewing balances reflecting interest accrual based on a full payment being made versus an installment payment. |
In Info Center, the toggle button displays only when set to Installment or Full. If set to None, the toggle button does not display. If set to Installment, when first viewing a Revenue Object in Info Center, the button is labeled Inst Pmt and the interest calculated is based on the expectation the taxpayer will pay by installment. If set to Full, when first viewing a Revenue Object in Info Center, the button is labeled Full Pmt and the interest calculated is based on the expectation the taxpayer will pay the bill(s) in full. You can click on the button to toggle the interest calculation from being based on installment payments to being based on a full payment for all bills with a balance due. If the displayed interest is based on installment payments, the button displays Inst Pmt. If the displayed interest is based on full payments, the button displays Full Pmt. In Cashiering, if set to Installment or Full, this determines the default interest calculated amount shown based on the expectation the taxpayer will pay the bill by installment or in full, respectively. The user may toggle between the two amounts. If set to None, the toggle becomes a means by which to toggle between the current amount due and the total amount due for the bill. Non-Colorado customers should accept the default of None. |
| Default Protested Payment flag | Effective Date/ Systype | Determines the Flag applied to bills that are under protest, in the Protest Tax Bills function. Choices are flags set up through Configuration; Flags. Must be a flag configured to be associated to tax bills. | Tax> Accounts Receivable> Protested Payments> Tax Bills Protest. Search on bill(s) and select the bills/charges to protest. When saved, the system will apply the Flag designated in the setting to the bills. |
| Default Protested Payment miscellaneous group | Effective Date/ String | Determines the Miscellaneous Source Group used by the Protested Payment Reconciliation process. |
Leave blank unless this process is used by the jurisdiction: Tax> Accounts Receivable> Protested Payments> Reconciliation. If used, set to a Miscellaneous Source Group (such as 'Protested Payment Miscellaneous Source Group') to be used. Configuration is also required under Tax> Accounts Receivable> Setup> Protested Payments Miscellaneous Source Mappings. |
| Default Surplus Subcode for defaulted plan payments to bills | Effective Date/ Systype |
When a payment plan that applies payments towards bills is not paid timely and becomes defaulted, plan payments are reallocated and all or a portion of the payments may be placed into surplus. This setting determines the default surplus subcode selection. It will appear in the Accounts Receivable Payment Plan Type setup screen (Tax > Accounts Receivable > Payment Plans > Plan Type Setup > Set Up Plan Type ) when configuring plan types where plan payments are applied to bills. Choices are systypes set up in Configuration> Systypes. |
Select the surplus subcode to use to hold plan payments for defaulted plans, after configuring the systype to be associated to the appropriate Surplus Code (Overage), and Surplus Category (Other). If a specific plan type should not use this default, an override surplus subcode may be entered on that plan type setup. |
| Display nominal overages in the Adv/Surplus area in info center | Effective Date/ Boolean |
Set to True you want this value displayed in the Advance/Surplus area in Info Center: a surplus which is over the amount due but within the specified tolerance amount. Set to False if you want these nominal overages excluded from display in Info Center (Total Due panel of Tax Information screen.) |
Set to False if you do not want to see nominal overages in the Advance/Surplus total in Info Center. Default is True. |
| Distribution delinquent Event type | Effective Date/ Systype | Date type for, for determining what is eligible for certain distributions. |
Set a date type configured in the Functional Calendar for all bills. Options are dependent on systypes specified. Used by Tax Accounting General Ledger Mapping for the 'IsDelq' attribute, and by the Tax Accounting GL Export. Also used by the Collections Summary Report for the 'Current/Defaulted' criteria and sort options - the Business Date of the payment will be compared to this date to determine if the payment is considered current or defaulted/delinquent. |
| Do not reapply surplus during Roll/Process Correction | Effective Date/ Boolean | Set to False to reapply surplus associated to payments during a Roll Correction or Process Correction. Set to True to if surplus associated to payments should not be reapplied during a Roll Correction or Process Correction. |
Default is blank/false. When set to blank/false, the system will automatically reapply surplus directly associated to payments, when payments are reapplied. When set to True, then during a Roll Correction or Process Correction, the system will not automatically reapply surplus directly associated to payments, when the payments are reapplied. Example: A bill is fully paid with an Overpayment of $100. A Roll Correction decreases the charges by $50. If False, the reapply of payments will also reapply the Overpayment of $100, and result will be a Correction surplus of $150. If False, the Overpayment of $100 will not be reapplied; it will remain at $100 and a Correction surplus of only $50 will be created. Only affects reapply of payments/surplus as a result of Roll Correction or Process Correction. |
| Do not recalc penalty in years prior to | Effective Date/ Integer | Causes the penalty and interest calculations to not recalculate penalty. However, interest continues to be calculated for tax bills prior to the year specified in this setting. This is to preserve converted data that has different charge identifiers than what Aumentum will generate on tax bills created in Aumentum. | Set the year if different than default. Default value is '2005'. |
| Do PIN translation for Remittance Import | Effective Date/ Boolean | This is a situation in which a third party vendor requires an all numeric PIN but the county uses both numeric and alphabetic characters. When set to true, Aumentum converts characters of a PIN in the Remittance Import file from all numeric to the combination of numeric and alphabetic character equivalents used in Aumentum; likewise for Remittance Export, the alphabetic characters within a PIN are converted to a numeric equivalent for the export file. | Set to ‘true’ to convert characters of a PIN in the Remittance Import file from all numeric to a combination of numeric/alphabetic equivalents used in Aumentum. |
| eGov Export future amount logic | Effective Date/ Systype | Determines the parameters shown and logic used for the eGov Tax Data Export, when populating amounts owed for future dates. |
Default is 'Use entered dates'. Alternate selection is 'Sarasota eGov future amounts'. Select this setting for Sarasota County, FL only. |
| eGov extract logging on | Effective Date/ Boolean | Enables logging for the eGov extract process for reporting purposes. | Set to true to enable additional logging (beyond standard logging done when Reach-In calls occur) for internal troubleshooting. Data is stored in eGovLog_T table. See also eGov extract - days to retain data. |
| EGov Flag to Inactivate from PIN when CollecMax Payment Received | Effective Date/ Systype |
Designates the flag to be inactivated, once the payment has been imported successfully through the eGov Payment Import or the MultiPay Web Payment Import. |
Select the flag type (example: 'Payment Pending' or 'Collect Max Payment Pending') to remove during the eGov Payment Import or MultiPay Web Payment import. When payments are taken online via the CollectMax/eGov/Public Access product, a stored procedure may be called which will add the designated flag on the PIN (Revenue Object). The existence of this flag is configured to prevent other payments from being taken, until the payment collected online is processed. When the online payment is imported, this setting will result in the flag being inactivated (regardless of which installment(s) are paid, or if it is a partial payment). |
| eGov logging – days to retain data for extract and reach-in | Effective Date/IntegerString | Defines the number of days the logging for the eGov extract is retained. | Define the number of days to retain eGov logging information stored in the eGovLog_T table. The default is 30. See also eGov extract logging enabled. |
| Enable automatic Senior Quad Payment Letter for Lockbox | Effective Date/ Boolean | Controls whether the system will automatically generate a Senior Quad Payment letter, when the payment source is Lockbox. |
Default is False. Missouri only: Set to True if the system should automatically generate a Senior Quad Payment letter when the payment source is Lockbox. Requires additional configuration of a Word template, and Report Setup, using the data source 'Senior Quad Payment'. Only 1 report setup using this data source should be configured. |
| Enable charging of Refund Fee | Effective Date/ Boolean | Controls whether the Refund Fee charge functionality is enabled. | Set to True if your jurisdiction may charge a Refund Fee. Set to False if a Refund Fee is never charged. Also see setting Refund Fee miscellaneous source charge code. |
| Enable Workflow notify of Pmt activity on PINs with Delq Flag | Effective Date/ Boolean | Controls whether 'Payment on PIN w DelqFlag' event is created. | Default is False. Set to True to cause the system to evaluate all payment activity, and if it occurs on a PIN with a designated Delq Flag (in the applicaton settings 'Notify of Pmt activity on Delq Real Property Flag' and 'Notify of Pmt activity on Delq Personal Property Flag'), the system will create an event. |
| Exclude Secured bills in Active payment plan from Collection Type Transfer | Effective Date/ Boolean | Controls whether Secured bills that are part of a payment plan are included/excluded in a collection type transfer via the Accounts Receivable > Collection Type Transfer task. | If set to true, Secured payment plan bills are excluded from the mass collection type transfer and will remain Secured while they are in an active plan. The default is false (payment plan bills are included in the transfer). Typically set to True for California, as Secured Escape bills in a valid escape payment plan are considered to have an extended due date and do not become defaulted as long as the plan is active and current. |
| Flag to Inactivate from PIN/Bill when Vendor Payment Received | Effective Date/ Systype | Defines which Flag to remove, if a payment is applied. |
Default is blank. If the Vendor Payment Import process should automatically remove a Flag from the PIN or Bill if a payment is applied, select which Flag should be removed. |
| Flag to use for batch payment blocking | Effective Date/ Systype | Defines the flag to apply to block other payments from being made towards a bill, while a batch collection payment import is in progress. Create a flag in Flag Maintenance, to add to each bill indicating payment is pending. This flag is applied during the Run Process step of the mass batch collection payment import payment process and prevents other methods from posting a payment. Once the mass payment is posted, the flag is removed. | A flag must first be defined and the flag must be set up in Flag Payment Rules to 'not allow payment'. Select the flag using this application setting. See also the Block payments during batch payment processing application setting as that is used in combination with this application setting when set to True. |
| Fund Activity Rpt display SPA Project Future Year Tax? | Effective Date/ Boolean | Controls whether Fund Activity Report includes SPA Project Future Year Tax. | If set to True, the Fund Activity report will include Special Assessment project Tax charges for future years not yet extended (billed) in the Beginning Balance or charge Adjustments column. If set to False, the report will not include Special Assessment project Tax charges for future years; only years that have been extended (billed) will be included. |
| Fund Activity Rpt include SPA Project Int with Late Pmt Int? | Effective Date/ Boolean | Controls whether Fund Activity Report includes SPA Project Interest as Charge Type of Interest or Tax. | If set to True, the Fund Activity report will include Special Assessment project Interest charges as Charge Type 'Interest' (grouped with late payment interest) instead of Charge Type 'Tax'. If set to False, the report include Special Assessment project Interest charges as Charge Type 'Tax' (how they are actually extended and stored). |
| Generate an event when a partial payment is detected | Effective Date/ Boolean | Determines whether to generate an event for partial payments received via the Cashiering > Collect Payments screen or via Batch Collections. | Set to True (default) for Aumentum to create a Aumentum Event for partial payments made through Cashiering or Batch Collections. (Required, if Partial Payment Workflow is to be used by the jurisdiction, to extend due dates and send letters.) Set to False to forego creating an event when a partial payment is received. |
| Generate an event when a payment is posted | Effective Date/ Boolean | Determines whether to generate an event every time a payment is posted through Cashiering or Batch Collections. |
Set to False (default) if no event is to be generated when a payment is posted. Set to True if an event is to be generated every time a payment is posted through Cashiering or Batch Collections. This setting was designed to be used with a workflow that needs to start for every payment posted through Cashiering or Batch Collection (not just partial payments), where the workflow will execute further decision points and actions depending on results. |
| Include defaulted plan credit in tax bill balance calculation? | Effective Date/ Boolean | (California only) Determines if Defaulted Payment Plan Credit (DPPC) surplus is to reduce the amount owed by the taxpayer for a Redemption Group (set of Defaulted Secured bills for a PIN). |
Default is False. Set to True for California jurisdictions: it is statutorily required for counties using Redemption Payment Plan functionality. When set to True, the amount due for the Redemption Group will be reduced by the amount of DPPC on Aumentum screens, reports, and exports. The credit will be prorated across the unpaid charges for the Redemption Group using the default Cashiering payment allocation rule. When the remainder owed for the Redemption Group is fully paid, the DPPC will be allocated towards the Redemption Group charges for distribution. To create DPPC, configuration is required in Tax> Accounts Receivable> Payment Plans. |
| Include delinquent fees and tax sale interest in batch PI calc | Effective Date/ Boolean | Indicates whether the calculation and posting of calculated and due (but not charged) delinquent fees and tax sale interest should be performed during the Payment Terms (Apply as Batch) process. | Set to True to include calculation and posting of delinquent fees that are calculated and due, and tax sale interest when the Payment Terms (Apply as Batch) process runs. Default value is False. |
| Include overbid in interest calculation for Certificate Refund | Effective Date/ Boolean | Indicates whether to include the overbid amount in the basis that is multiplied by the rate, when calculating the interest for a tax sale certificate refund. | Only applies to Certificate/Lien Tax Sales; does not apply to Property Sale. If a certificate purchase is voided and refunded back to the buyer, interest may be calculated and added to the refund amount. Set to True to include the overbid amount as part of the basis that is multiplied by the rate, when calculating the interest for a tax sale certificate refund. |
| Include payment plan forecasting in batch PI calculation | Effective Date/ Boolean | Indicates whether the system will perform a forecast of payment plan amounts due, during the Payment Terms (Apply as Batch) process. | Default is False. Set to True if payment plan amounts are to be exported to Public Access via the eGov Tax Data Export. |
| Include secure/unsecure assignment in batch PI calculation | Effective Date/ Boolean | (CA only) Will automatically change the collection type of unpaid charges from Secured to Unsecured or vice versa, when bills meeting the Collection Type Assignment criteria are identified during the Payment Terms (Apply as Batch) process to calculate accrued penalty and interest. | Set to True for California. If during year-end there is a period of time the county does NOT want the system to automatically transfer the collection type (for example, while catching up on entering timely payments), then temporarily set this to False and remove the criteria from the Collection Type Assignment setup. Replace the criteria and change the setting back to True to resume normal operations. |
| Installment Balance of Charges Date | Effective Date/ Systype | Specifies the date used by the 'Balance of Charges as of' setting in Payment Terms Rules. |
Used by Payment Terms Rules when configured to verify whether an installment has an unpaid balance as of a date, before accruing penalty, interest, or discount. Must be set to a date configured in the Functional Calendar for all bills that will be evaluated by the Payment Terms Rule. Typically set to Due Date. |
| Lender Export Filtering | Effective Date/ Systype | Controls the options available to users on the parameter entry screen of the Lender Data Export. | Choices are None/Only Real/Only Annual Real. Default is None. If None is selected (or setting is blank), then users will be able to select any Roll Caste, and any Roll Type. If Only Real is selected, then users will be able to select any Roll Caste, but only Roll Type = Real for the export. If Only Annual Real is selected, then users will only be able to select Roll Caste = Annual and only Roll Type = Real for the export. |
| Mortgage Export Filtering | Effective Date/ Systype | Controls the options available to users on the parameter entry screen of the Mortgage Escrow Data Export. | Choices are None/Only Real/Only Annual Real. Default is None. If None is selected (or setting is blank), then users will be able to select any Roll Caste, and any Roll Type. If Only Real is selected, then users will be able to select any Roll Caste, but only Roll Type = Real for the export. If Only Annual Real is selected, then users will only be able to select Roll Caste = Annual and only Roll Type = Real for the export. |
| Notify of Pmt activity on Delq Personal Property Flag | Effective Date/ Systype | Determines which Flag the system uses to identify Delinquent Personal Property, for purposes of generating an event and workflow to notify county that a payment activity has occurred on that PIN or Bill. | Default is blank. If the application setting 'Enable Workflow notify of Pmt activity on PINs with Delq Flag' is set to True, then select the Flag Type that represents a PIN that is on the Certified Foreclosure list for Personal property. |
| Notify of Pmt activity on Delq Real Property Flag | Effective Date/ Systype | Determines which Flag the system uses to identify Delinquent Reak Property, for purposes of generating an event and workflow to notify county that a payment activity has occurred on that PIN or Bill. | Default is blank. If the application setting 'Enable Workflow notify of Pmt activity on PINs with Delq Flag' is set to True, then select the Flag Type that represents a PIN that is on the Certified Delinquent list for Real property. |
| NSF Notice Generation Date Plus | Effective Date/IntegerString | Used with the 'NSF Notice' and 'NSF Notice - Plan Payment' data services. How many days to add to the notice generation date, when populating the field 'Notice Date Plus N Days'. | Default is blank. Set to the number of days desired for the jurisdiction, if the 'Notice Date Plus N Days' is used in correspondence. |
| NSF\Cancel-NS process to reapply remaining to selected bills | Effective Date/ Boolean |
When only a portion of a payment towards a bill is removed using the Bad Check or Cancel-No Surplus functions, indicates whether the remainder of the payment originally allocated to that bill is to be reapplied to that bill. If not reapplied, it will be placed into surplus. By default, when only a portion of a payment is removed / canceled using the Bad Check or Cancel-No Surplus functions, and the Reapply cash portion automatically for Bad Checkapplication setting is set to True, the remaining uncanceled portion of the payment will be reapplied back to the specific original bill it paid. However in California (and other jurisdictions based on business rules) if a set of bills are paid together and a portion of the payment is canceled, the remaining uncanceled portion of the payment must be reapplied back to the entire SET of bills using the payment allocation rule logic. (In California, this set of bills is called a Redemption Group, consisting of any unpaid Defaulted Secured bills for a PIN.) Set to True to enforce reapplying the uncanceled portion of the payment to the set of bills. Set to False if the system should reapply the uncanceled portion of the payment only to the bill it originally paid. Note: The user must select and display the entire set of bills paid in the Bad Check or Cancel-No Surplus screen for this application setting to function as designed. When set to True, the system will reapply the uncanceled portion to the set of bills on the screen.
|
Set to True for California. For other jurisdictions, set based on the jurisdictions business rules. Example: 3 bills have $100 paid, with $75 by check and $25 cash. The payment does not pay the bills in full, and based on the payment allocation rule is prorated across the 3 bills. If only the $75 portion is canceled, should the remaining $25 be reapplied and prorated to the bill charges of all 3 bills, based on the payment allocation rule. See also the Reapply cash portion automatically for Bad Check application setting as that is used in combination with this application setting when set to True. |
| Number of Unpaid Installments Date | Effective Date/ Systype | This is the "as of" date used to calculate the number of unpaid installments by Payment Terms Rules. | Set the date used to calculate the number of unpaid installments - example: How many installments are unpaid as of the Penalty Start Date. Must be a date that is configured in the Functional Calendar for all bills that will be evaluated by the Payment Terms Rule. |
| Office Contact for N Day Notice | Effective Date/ Systype | The Office Contact used by the Partial Payment N Day Notice Data Service correspondence. | Default is Blank. Select if the jurisdiction is using the 'N Day Notice' data service to generate correspondence (typically used with Partial Payment Workflow functionality). |
| Overwrite Surplus Management search results restriction | Effective Date/ Boolean | The Surplus Management Search results are limited to the number of records defined by the System application setting 'Search result limit'. Set to True if the Surplus Management Search should ignore that application setting and return all matching records. | Default is False. Setting to True may result in long-running searches for Surplus Management. |
| Partial Payment Workflow Extend Due Date # Days | Effective Date/ Integer | Used by the Partial Payment workflow, this setting determines the ending date of the Payment Terms Token that is assigned to extend the due date. The ending date will be the date the correspondence letter is generated plus the N days specified. | Default is blank. Typically set to 10 days for California counties using the Partial Payment workflow. Will have no impact if the Partial Payment workflow is not being used. |
| Payment Import Image method | Effective Date/ Systype | Choices are XternaLink or Aumentum Attachments. Determines the method of identifying images associated to payments. | Set to Aumentum Attachments unless working with a jurisdiction specifically using XternaLink. Will have no impact unless the jurisdiction is configured to import payment image information. |
| Payment Plan APR rounding precision | Effective Date/ Integer | Set the rounding option; for example, round to 3 decimal places = 11.667% (MN). | Set to the number of decimal places that results in the correct rounding for your state. See examples. Default is 10. |
| PI support logging on | Effective Date/ Boolean | This setting is for Aumentum Technologies support use only. It is not used for batch processes. | Do not change. |
| PIN Link on Post Refunds goes to | Effective Date/ Systype | Defines whether to navigate to the Info Center > Tax Information or the Info Center > Bill Detail screen when clicking the PIN active text hyperlink on the Accounts Receivable > Post Refunds screen. | Select either Information Center Tax Detail (default), or Information Center Bill Detail to define the screen to advance to from the Post Refunds screen. |
| Prorate Refund Interest to TAF/TIF and include in Distribution? | Effective Date/ Boolean |
Controls whether refund interest should be prorated to a TAF/TIF and whether to include it in distribution. If refund interest is to be stored as a single row in FnclTranDetail with TAG/TAF/TIF set to 0 and no data being written to the RefundIntDist with the exception of the Palm Beach County subroutine then set to False or Blank; or If refund interest is to be prorated across TAG/TAF/TIF when written to FnclDetail and broken out in RefundIntDist, then set to True. |
When set to True, and refund interest is added to a refund transaction, a proration algorithm is performed that breaks out the single Refund Interest row in FnclDetail into multiple rows in RefundIntDist. This breakout is calculated bbased on a prorated % of the surplus being refunded, derived from the payment rows of the transaction that created the surplus. If set to True, the Refund Interest Rule setup will have the Calculation Rule Detail screen configured to include the Prorate Refund Interest to TAF/TIF? checkbox selected. When set to True, when processing a refund on the Post Refund screen, the Refund Details panel will display whether refund interest will be prorated with the word Prorated next to the refund interest amount. This can be overridden by clicking Edit Refund and clearing the 'Prorate to TAF/TIF? checkbox. In addition, the Payment Listing Report parameter screen will include a 'Refund' option in the Payment Management Transactions section, and the reports (except Other Fees Recap) will include prorated refund interest (but not all refund information) associated to a TAF/TIF. On the Payment Listing reports: 1.) The column label heading 'Fee/Misc' changes to 'Fee/Misc/RefundInt', and the refund amount is reported as a negative number on the Payment Recap and Payment Recap by Installment reports; 2.) The column label heading 'Discount' changes to 'Discount/RefundInt', and the refund amount is reported as a negative number on the Roll Type Recap, Tax Authority Recap, Fund Recap and TIF District Recap reports; On the Collections Summary Report, Refund/Interest will be included in the Collections Summary report whenever the Charge Type equals Surplus. The heading 'Reapplies' changes to 'Reapplies/RefundInt' on the report. Refund Interest that has a TAF/TIF in RefundIntDist is grouped in the applicable row of the report with the other TAF/TIF amount. Refund Interest that does not have TAF/TIF continues to display in the report as it currently displays, and Refund Interest amounts show as negative, decreasing the Net. The Refund/Overpayment Listing report will continue to show a single line for the Refund Interest amount. If multiple rows exist in FnclTranDetail, they are summed together for the Refund Interest. Predistribution: A 'Process Filter' dropdown on the Set Up a New Predistribution screen allows filtering by just the Distribution Category of Refund Interest. Distribution History Reports can also be filtered by the Distribution Category of Refund Interest. |
| Prorate Refund Interest to TAF/TIF and include in Tax Accounting? | Effective Date/ Boolean |
Controls whether refund interest should be prorated to a TAF/TIF and whether to include it in tax accounting. If refund interest is to be stored as a single row in FnclTranDetail with TAG/TAF/TIF set to 0 and no data being written to the RefundIntDist with the exception of the Palm Beach County subroutine then set to False or Blank; or If refund interest is to be prorated across TAG/TAF/TIF and broken out as Prorated amounts in FncTranlDetail, then set to True. NOTE: For 'Prorate Refund Interest to TAF/TIF and include in Tax Accounting?' to be set to True then 'Prorate Refund Interest to TAF/TIF and include in Distribution?' must ALSO be set to True. |
Set to True if refund interest must be shown as prorated on the Fund Activity Report, and passed as prorated amounts to Tax Accounting. |
| Provide multiple Class Codes in eGov Extract | Effective Date/ Boolean | This setting provides the ability to export Class Codes (aka Use Code in MN) in the eGov Export |
When set to False, this indicates that the Class Code column on the Revenue Object table for the eGov Export will be used to populate the ClassCodeShortDescr1 and ClassCodeDescr1 columns. The ID value in the Class Code column is used to look up the corresponding SysType so the ShortDescr and Descr columns are written in the ClassCodeShortDescr1 and ClassCodeDescr1 columns. The remaining 4 sets of additional fields will be blank. When set to True (as it will be, for example, in Minnesota), the following process is used to populate the ClassCodeShortDescr and ClassCodeDescr columns: 1. For each tax bill to be added to the eGovBillData table, the most current CadInv record is found. 2. For each matching record in the ValueTypeAmount table that matches the CadInv item, the rows where the ValueTypeID column is USECD is found. 3. The number of USECD rows returned for each CadInv record is then determined. 4. If the number of USECD rows returned is: Between 1 and 5, the shortdescr and descr values from each of the systype corresponding to the value in the AddlObjectId column into the ClassCodeShortDescr and ClassCodeDescr occurrences is written. More than 5, the first four as described above are written. Add the literals “AddClsCodesExist” and “Additional Class Codes Exist For This Item” to ClassCodeShortDescr5 and ClassCodeDescr5 respectively. |
| Reallocate pmt to original inst during correction if exceeds charges | Effective Date/ Boolean | Provides the option to reallocate payments back to only their original installment when a correction occurs that results in the total payments being greater than the total new charges. This results in a separate surplus being created for each installment that has excess payment, allowing refund interest to be calculated based on the payment date of each individual payment date of each individual payment if configured to do so. | When set to True and the total amount paid (on the given tax bill prior to the correction) is greater than resulting total charged (on the given bill after the correction), for each payment against the bill, the Reallocate step of corrections determines how much was allocated to each installment prior to the correction. For each payment\installment combination, the amount is reallocated back to that same installment. Any amounts that cannot be reallocated to the given installment create a surplus. Unallocated amounts for a given payment across all installments are combined into a single surplus record. If the total amount paid is not greater than the resulting total charges, the reallocation is processed using existing functionality that uses the Automatic payment reallocation options application setting. If set to False, the reallocate step of corrections uses existing functionality that applies the Automatic payment reallocation options application setting. Set as applicable to your jurisdiction. |
| Reapply cash portion automatically for Bad Check | Effective Date/ Boolean |
The setting is relevant when a bad check occurs on a payment with multiple tenders (example: cash and check). During the Bad Check process, the user may choose to cancel only the check portion of the payment by updating the Cancel Amount. If the setting is True, the remaining uncanceled 'cash' portion of the payment is automatically reapplied to the bill it originally paid. If the setting is False, the remaining 'cash' portion of the payment is put into surplus, where it can be manually reapplied using Payment Management. |
Default is False. Set to 'True' for the uncanceled 'cash' portion of a multiple tender payment to be automatically reapplied to the original bill. Use the default setting of 'False' to leave the cash portion in surplus until reapplied using Payment Management. Example: A bill has $100 paid, with $75 by check and $25 cash. If only the $75 portion is canceled, should the remaining $25 be reapplied to the bill charges, or should it be placed into surplus. This se (California) See also the NSF\Cancel-NS process to reapply remaining to selected bills application setting which is used in combination with this application setting when set to True. |
| Reason Code for Buyer Payment Import Threshold Exception | Effective Date/ Systype |
(California only.) Used in combination with the Delinquent application setting Advertising Use Minimum Bid Factors, the Property Sale Require Override for Reducing Minimum Bid in Mass Entry, and the minimum bid factor amount threshold set on the Maintain Property Sales screen, if set to true, if the threshold is exceeded when defining the minimum bid on the Mass Enter Tax Sale Information screen, a popup displays requiring a reason code. |
(California only.)Select the reason code as applicable to your jurisdiction. The selections are entered by the jurisdiction in the systypes for 'Below Min Bid Threshold Reason Codes'. |
| Record discount as receivable | Effective Date/ Systype | Indicates when discounts should be written to the database, at which time the discount is considered receivable. The discount is written to the database when paid by default. Values are: 1.) 'When paid' - to record as a receivable only when paid, and 2.) 'When paid or due" - to record as a receivable when the charge is paid or the due date for the charge has passed. | Select correct setting. Default value is 'When paid'. Setting should be determined during Implementation prior to go-live. |
| Record interest as receivable | Effective Date/ Systype | Indicates when interest should be written to the database, at which time the charge is considered a receivable. If an interest charge is calculated and shown in Cashiering, but the selected condition is not met, then the full, calculated charge will not be recorded in the database; however, a partial amount might be recorded. Possible values are: 1) 'When paid' - to record only as a receivable when the charge is paid. 2) 'When paid or due' - to record as a receivable when the charge is paid or the due date for the charge has passed. | Select correct setting. Default value is 'When paid'. Setting should be determined during Implementation prior to go-live. |
| Record penalty as receivable | Effective Date/ Systype | Indicates when penalty should be written to the database, at which time the charge is considered a receivable. If a penalty charge is calculated and shown in Cashiering, only the portion that gets paid is stored in financial detail (FnclDetail); the other charges go to the non-receivable table, where they remain until they are actually paid. Possible values are: 1) 'When paid' - to record only as a receivable when the charge is paid. 2) 'When paid or due' - to record as a receivable when the charge is paid or the due date for the charge has passed. | Select appropriate setting. Default value is 'When paid or due'. Setting should be determined during Implementation prior to go-live. |
| Redemption Penalty (Interest) Charge Code | Effective Date/ Systype | (California only) Indicates the charge code of the charge that is considered 'Redemption Penalty (Interest)'. Charge codes are systypes set up through Configuration> Systypes. |
The 'Redemption Penalty (Interest)' charge is a California charge of 1.5% accruing monthly on bills when unpaid after their defaulted date. Review Tax> Accounts Receivable> Payment Terms Rules and select the charge code that is associated with the Redemption Penalty (Interest). |
| Refund Claim # of Days | Effective Date/ Integer | (California only) Determines the required Return Date for the surplus/refund claim form. The Return Date will be the Claim Form Sent Date + the # of days entered. |
Typically set to 45 days (or more if there is a grace period given) in California jurisdictions. The Return Date is used by Refund Interest Rules, to help determine if refund interest is to be added. (A taxpayer who fails to return the claim form timely may not be entitled to refund interest for some types of refunds.) |
| Refund Fee miscellaneous source charge code | Effective Date/ Systype | Indicates the charge code to be used when a Refund Fee is charged and paid using the surplus as tender prior to a refund. | Only needs to be set if the jurisdiction will charge a refund fee. Also see the setting Enable charging of Refund Fee. |
| Refund Interest Refund Business Date Plus | Effective Date/ Integer | Used when number of grace period days are needed when calculating interest. For example, a refund is created on 10/26, but the check will not be cut until 5 days later. Refund business date plus grace must be used as the "to" date in the setup. Note: Use this application setting only when calculation of interest (the day it starts or the day it ends) involves the Business Date that the refund is being processed via Tax> Accounts Receivable > Manage Payments > Refund. The Plus in the application setting is the number of days the system will add onto the refund business date when determining the number of days of refund interest to add. | Enter a numeric value that represents the number of days grace period. No value is the default. For example, some counties allow an extra 5 days for how long it takes them to physically process and mail the check. |
| Require Reason Code if Edit/Refund Surplus Correspondence | Effective Date/ Boolean | Allows the jurisdiction to select whether they want to save a Reason Code for Refund/Surplus correspondence modifications. | Set to Yes if your jurisdiction requires a reason code for refund/surplus correspondence modifications. No is the default. |
| Require reason if reinstate payment plan? | Effective Date/ Boolean | Determines if a reason code is required, if a payment plan status is changed from Defaulted to Active. |
Default is False. Set to True if the system should require entry of a reason, if the payment plan status is changed from Defaulted to Active. Reasons for plan reinstatement are defined by the county, in Configuration> Object Scope Maintenance. |
| Roll type for state credit charges | Effective Date/ Systype | (GA only) Select the roll type that should be used when creating state credit charges. This is an action taken as part of the PT-553 report. | Select the roll type for the Georgia PT-553 report. No default value is specified. |
| Rollback interest charge code | Effective Date/ Systype | Specifies which charge code in financial detail (FnclDetail) distinguishes Rollback Interest charges to provide information for Aumentum Delinquent installment balances. This setting is also needed for the rollback tax bill. | Select the appropriate charge code. No default value is specified. May apply only to Virginia jurisdictions. |
| Secured/Defaulted Secured Write-Off Upper Threshold | Effective Date/ Decimal | (California only) Defines the upper Tax amount threshold for write-offs on secured/defaulted secured bills. |
Default is blank. When no amount is entered, any amount may be written off. When an amount is entered, the value will determine the maximum Tax amount for which Write-offs are allowed on Secured/Defaulted Secured bills, in both Delinquents and Process Corrections. Any record being written off with a Tax amount over the value will not be written off, unless an override with a selected reason code is used. The threshold value is for Tax charges only. Other charges such as Fees, Penalty, or Interest are not considered when comparing to the threshold amount. When performing a Write-off in Delinquents, records will appear on the Threshold Report which is generated along with the Write-off report to allow the user to see the records excluded due to the threshold setting. See also the Unsecured Write-Off Upper Threshold application setting, |
| State Controllers Revenue Account | Effective Date/ String | (California only) Specifies the revenue account for the state controllers office to run the Semi-annual Settlement Report. | Enter the Revenue Account number configured for the California State Controllers Office. |
| Surplus SubCode for Surplus Created Alert | Effective Date/ Systype | Defines the surplus subcode associated with the surplus for the Surplus Created system alert. | If the jurisdiction wishes for an email alert to be sent to users in a department when a specific type of surplus is created, then set to the applicable subcode for the Surplus Created system alert. NOTE: System email alerts are set via Configuration > System > Alert Maintenance. System alerts require additional email server configuration. |
| Surplus SubCode for Unclaimed Refund data service | Effective Date/ Systype | Defines the surplus subcode associated with the 'Unclaimed Refund' data service that is used in Mass Refund processing. | Default is blank. Select the appropriate Surplus SubCode for the jurisdiction, if using the Mass Refund processing data service 'Unclaimed Refund'. |
| Tax bill dates adjustment - Additional grace period (days) | Effective Date/ Integer | The number of additional grace period days given for tax bill date adjustments resulting from a correction in FL. |
(Florida only) The default is zero (0). Set for the number of additional grace period days allowed for a corrected bill. This setting is used by Levy during a correction, to reset the dates associated to the tax bill. In FL, when tax bills are corrected, the correction date is used as the basis for discounts and interest. If the bill would have received discount, it gets an extra N days to receive that discount. If the bill would have been charged interest, it gets an extra N days before interest is computed. |
| Tax bill dates adjustment - Grace period (days) | Effective Date/ Integer | The number of grace period days given for tax bill date adjustments resulting from a correction in FL. |
(Florida only) The default is zero (0). Set for the number of grace days allowed for a corrected bill. This setting is used by Levy during a correction, to reset the dates associated to the tax bill. In FL, when tax bills are corrected, the correction date is used as the basis for discounts and interest. If the bill would have received discount, it gets an extra N days to receive that discount. If the bill would have been charged interest, it gets an extra N days before interest is computed. |
| Tax sale collection fee name for estimated redemption amount | Effective Date/ String | Enter the fee name for the tax sale collection fee (example: COLLECTION FEE-RE). |
Default value is COLLECTION FEE-RE. Used by an Estimated Redemption Amount calculation which, prior to tax sale, projects how much would be due for an unpaid bill if it were to go to sale and be turned into a certificate. The bill does not have the collection fee on it yet, so the setting tells the system which fee to use to 'virtually' add to the amount. Requires the Info Center application setting 'Show the estimated redemption amount grid' to be set to True. |
| Test to use alternate dates | Effective Date/ Systype | If the jurisdiction requires use of an alternate date for some bills, this is the test the system will perform to determine if the alternate date(s) applies to the bill. |
Set to 'Never use alternate dates' unless required by the jurisdiction. Alternate choices are: '1st Installment Bal Due <= Penalty Tolerance' or 'Personal 1st installment paid on or before due date' (used in Kansas). Each of these choices follow specific logic to evaluate if an alternate date is to apply. If set to something other than 'Never use alternate dates', Functional Calendar configuration must have alternate dates included in the set up for all of primary dates used which have an alternate (even if the alternate date will be the same). |
| Unsecured Write-Off Upper Threshold | Effective Date/ Decimal |
(California only) Defines the upper Tax amount threshold limit for write-offs on Unsecured bills. |
Default is blank. When no amount is entered, any amount may be written off. When an amount is entered, the value will determine the maximum Tax amount for which Write-offs are allowed on Unsecured bills, in both Delinquents and Process Corrections. Any record being written off with a Tax amount over the value will not be written off, unless an override with a selected reason code is used. The threshold value is for Tax charges only. Other charges such as Fees, Penalty, or Interest are not considered when comparing to the threshold amount. When performing a Write-off in Delinquents, records will appear on the Threshold Report which is generated along with the Write-off report to allow the user to see the records excluded due to the threshold setting. See also the Secured/Defaulted Secured Write-Off Upper Threshold applicaton setting. |
| Use Batch No and Batch Seq No for External Links Images | Effective Date/ Boolean | Determines whether to update Image reference information during batch collection, with the process fields Batch Number and Batch Sequence Number . IMPORTANT: The Implementation Team configures the Batch Number and Batch Sequence Number as part of the Payment Detail section of the batch collections payment import file i/o layout (not part of the Header, Tender, or Trailer section). To view existing payment images, data must be converted into the Image table, with the Batch Number and Batch Sequence Number being associated to the Receipt Detail ID of each payment. |
Set to True, False or Blank (default) If false or blank, the system stores Batch Number and Batch Sequence Number data in the Payment Information table only. If true, and the application setting 'Payment Import Image method' is st to Xternal Link, the system also stores the Batch Number and Batch Sequence Number data in an Image table, associated to the ReceiptDetail of that payment. This data is used as Key1 and Key2 respectively, in Configure External Links, for payment Image configuration so that payment images can be retrieved. |
| Use certificate interest rate if less than refund interest rate | Effective Date/ Boolean | Set to True if the jurisdiction wishes to use the lower of the Certificate refund interest rate vs the Refund Interest Rule rate, when calculating refund interest for tax sale certificates. | (Florida only) If the corrected bill that results in a surplus is a tax sale bill (identified by CalcTaxSaleRefundInt on the surplus table), Aumentum will use the Refund Interest Rules to determine if the surplus should calculate Refund Interest. If yes, the system will look at the 'Use certificate interest rate if less than refund interest rate' application setting. If it is False, then the rate in the 'Certificate refund interest rate' application setting will be used. If it is True, then the rate from the 'Certificate refund interest rate' application setting will be compared to the rate from the refund interest rule, and the system will use the lower rate. The start date of the refund interest calculation will be determined by the 'Certificate refund interest start calculation event type'. Note: The rate entered will be divided by 12, and the refund interest calculation will be # of months x rate x surplus amount. Refund Interest for tax sale bills will be broken out and stored in the RefundIntDist table, using logic specific to Florida Lien Sale. |
| Use Functional Calendar Tax year when creating Surplus | Effective Date/ Boolean | Directs the system to use the tax year from the 'Tax Year' Functional Calendar (fiscal year) to newly created surpluses, rather than the system assigning the tax year of the associated paid tax bill or system date. |
Default is false. Leave False to use the tax year of the tax bill or system date when creating surplus (default functionality). Set to True to use the Functional Calendar tax year when creating surplus. |
| Use Paid on Behalf of as the default address for refunds | Effective Date/ Boolean | Determines if Paid on Behalf Of is used (when it exists) for the refund recipient instead of the PaidBy, if Default Refund/Claim Recipients configuration is not available. |
Paid on Behalf Of is populated only by the Lender Payment Import. It is when a Service Company pays 'on behalf of' a Lender, and so the Lender information is stored (at the ReceiptDetail level) of the items paid. Set to True if the Paid on Behalf Of should be used as the default address for refunds, instead of the PaidBy, IF the Paid on Behalf Of exists. If it does not exist, then the PaidBy will be used. Note: In Aumentum versions with Default Refund/Claim Recipients configuration, this setting is obsolete. The configuration done under Tax> Accounts Receivable> Surplus/Refund Setup> Default Refund/Claim Recipients takes precedence over this application setting. |
| Validate if surplus is in aging period before Refund is allowed? | Effective Date/ Boolean | Determines whether the system will check to see if a surplus is in an aging period before a refund is allowed. |
Default is False. If set to True, the Post Refund process will verify if the surplus is still within an aging period (based on Surplus Routing Rules, and Surplus.SurplusWFStatus). If it is, Security configuration permissions are required to override and complete the refund. |